Night Owl 19

home *** CD-ROM | disk | FTP | other *** search

/ Night Owl 19 / Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO / 007a / cbk_612p.zip / CALLBACK.DOC < prev next >

Wrap

Text File | 1995-12-15 | 29KB | 902 lines

CallBack(c) v6.12 & 6.12p MAXimus 3.00 User Verifier WYSIWYG By: Gary Zarzycki FidoNet 1:300/43 CallBack Contents Introduction.......................................... 3 Copywrite............................................. 4 CallBack Configuration File........................... 5 System Section.................................... 5 Modem Section..................................... 6 Verification Variables............................ 6 Optional Status Messages.......................... 8 Calling Variables................................. 9 Installation.......................................... 12 Executing CallBack.................................... 13 Operation (Consol Keys)............................... 15 CBKDAT.EXE Maintainance Program....................... 15 MAKEDAT.EXE Utility Program........................... 16 (i) CallBack 1.0 General. 1.1 Introduction. CallBack(c) is a User Verification system for use with MAXimus 3.00. It comes in two flavors, DOS and OS/2. The DOS version of CallBack hooks into your fossil so it supports all comports supported by your fossil. While, the protected mode OS/2 version supports all Ports via the handle passed by MAXimus using the %P parameter. CallBack supports all baud rates as configured and used by MAXimus. CallBack is loaded via a MAXimus Xtern_* command with the fossil, (DOS), or Comport, (OS/2) hot and prompts the user for their phone number and Date of Birth and checks each before continuing. If the phone number is found in the CallBack.Dat file, either under the [TRASHCAN] or [VERIFIED], the verification process is aborted with one of two possible actions. First, if the users phone number is found in the [VERIFIED] list, it tells the user their phone number has already been verified and returns them to the BBS, with a optional private status message to the user. If it finds the users number in the [TRASHCAN], it tells the user, then proceeds to TWIT their access, drops DTR on them causing MAXimus to recycle. In a successful verication, CallBack returns the user to the BBS with a optional pvt message to the user from CallBack, as configured by the SysOp. When a successful verification occures, CallBack writes the User Phone Number into the LASTUS??.BBS and USER.BBS files along with entering it into the CallBack.Dat file. While doing this, if CallBack finds a phone number in the Data Phone field of the USER.BBS, it will also write this into the CallBack.Dat file to prevent this number for additional verifications by the user. MEX programs and configurations are possible to prompt a New User for both, Voice and Data phone numbers to enhance the security of CallBack validations. CallBack has honesty check of the user if so configured as follows. If the users Date of Birth has not been priviously entered into their user record, CallBack will do this during verification. If the users Date of Birth was priviously entered, via a MEX routine or whatever, CallBack will compare what was priviously entered, and what currently was entered by the user. If they compare, CallBack continues. If there is a discrepancy between the dates, CallBack gives the user three chances to enter their Date of Birth and if the user fails after three tries, CallBack drops DTR and TWITS their access. (3) CallBack 1.0 General. 1.1 Introduction. CallBack does not use the old Password way of verification which is common within verifiers. Instead, CallBack uses a more secure way by generating a user code on the fly for the user to use, which is also a meaningful number for Sysops to use for future reference of the user and the date they were validated. A CallBack generated number would looks something like the following and is actually the month, day, one digit year and a three digit number representing the number of verifications for that day. 09015002 The above number would mean the second successful validation for first day of September, 1995. For obvious security reasons, Callback will not allow any area code or prefix to start with a zero, (0), or the numbers 911. Some verifiers have over-looked this nasty user trick with the SysOp waking up in the middle of the night with Police at their front door. If a user tries to enter a 0 as the first digit, or a 911 as the first three digits, CallBack will TWIT the user and drop DTR on them. 1.2 CallBack - Copywrite 1989 Although, for my protection I have CallBack Copywrited, it is being distributed as FreeWare for use by MAXimus Sysops in non-commercial environment. You may not modify or disassemble CallBack for any reason without written permission. If someone wishes to use CallBack commercially, they must contact me concerning a license to do so, and are prohibited from using CallBack unless a single user or site license is obtained from me. Fees for such is as follows: Commercial single user fee.................... $ 25.00 Commercial Multi user site fee................ $100.00 (4) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.1 System Section. SysOp <sysop name> This is your name you wish to use for CallBack and the optional verification status message for the user. BBS <bbs name> The name of your BBS. Snoop <Y or N> If you wish to view the User during the validation process. If you wish do have this option, enter Y for Snoop, or N if you do not wish to use this option. Note: The Console Alt S toggle will toggle snoop on/off. BBSLogFile <drive:path\filename> Where CallBack will log the user verification process and staus. This can be your MAX.LOG or Front End Log if you wish. LogStyle FD By Default, Callback writes the log in MAX style. If you wish to log to your Front End Log file in InterMail/FrontDoor Style, UnComment the line. LastUser <drive:path\filename> This is full path and filename to your LASTUS??.BBS file. Bells <Y or N> Bells <StartTime-StopTime> Do you want to hear beeps during Validation. Answer Y or N. If you wish to limit the hours, set a Start and Stop times, enter as such: Bells start_time-stop_time. EXAMPLE: To start at 8:00am and stop at 8:00pm enter: Bells 8:00-20:00 (5) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.2 Modem Section. COM # # represents the Com Port You want to use for your calling 1 2 3 etc. In DOS Mode, CallBack supports all COM Ports your fossil supports. In OS/2 protected mode, this option isn't used, but Callback supports COM 1 through COM 4 via the handle passed by MAXimus. DOS Default = COM1. ModemInit <init string> Optional Modem Init String. This will only be needed if for some reason you need to change the default Initialization from your configuration in MAX. Most cases, leave this commented out. Dial <dial string> Optional Dial String for Callback. Most cases, and the Default is ATDT. If you need to use Palse Dial, then it would be ATDP. 2.3 Verification Variables. MoveAnswers <option> If you have a pre-CallBack questionaire file via a MEX or Mecca file which write a answer file, optionally you can have CallBack move and group your answer files automatically for you by day, week or month. Options are as Follows: Move Option FileName Example ~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~ MoveAnswers No CallBack bi-passes MoveAnswers Day 08-25-95.DAY MoveAnswers Week 08-27-95.WE MoveAnswers Month Aug_95.MO Answers <drive:path\filename> If the above questionnaire answer file exists, this tells CallBack where and what to look for. (6) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.3 Verification Variables. CBKLog <drive:path> This is the drive and path to the CallBack.Dat data file of [VERIFIED], previously verified phone numbers, or SysOp entered [TRASHCAN], phone numbers. Privel <level number> Enter the level to raise the users priveledge if verified. Levels are 0 to 65535 as you have defined in your MAXimus ACCESS.CTL file. a Value 30 is the MAX default for 'NORMAL' priveledge. Enter value as a ASCII value and not in a HEX value. Max2Privel <privel name> Since MAX 3.00 Keeps it's USER.BBS and LASTUS*.BBS Backwards Compatable, we'll need to add MAX v2.00 level into the USER data base. Since MAX 3.00 is User Definable, enter the equivalent MAX 2.00 level as you have MAX 3.00 set up. Allowable Max2Privel Privel Names are as follows: "TWIT" "DISGRACE" "LIMITED" "NORMAL" "WORTHY" "PRIVEL" "FAVORED" SessionTime <minutes> If you wish to re-adjust the users time remaining after a successful verification, uncomment SessionTime and enter the minutes you wish to set the users time. The minutes entered here should be the same as you have configured for MAXimus for the verified priveledge level. EXAMPLE: SessionTime 40 The above would reset the user time remaining to 40 minutes. (7) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.4 Optional Status Message Section. MessagePath <drive:path> Full DRIVE:PATH of the Message Subdirectory to use if you wish to leave the New User their Status message after a CallBack Validation Attempt is made. CallBack will Create the Text Body message using the PassedMsg, or FailedMsg below. If you do not wish to use this Option, then leave this, the PassedMsg, and the FailedMsg commented out. If you use a Squish Message Data Base instead of a *.MSG 's, then include the data base name in the drive:pathline. NOTE: All Squish Type Areas will have the extension of .SQD. *.MSG TYPE EXAMPLE: C:\MAX\MSG\GENERAL The Above 'GENERAL' would be a Subdirectory of a *.MSG message area. .SQ (squish) TYPE EXAMPLE: C:\MAX\MSG\GENERAL.SQD The Above 'GENERAL.SQD' would be a Squish Data Base in the Subdriectory of 'MSG'. FailedMsg <drive:path\filename> The DRIVE:\PATH\FILENAME of Text "Body" for the Message to leave the New User after a Failed Attempt by the CallBack Verification System. Callback will append this message with a general status of why the verification failed. Sample is Called: FAILMSG.CBK FailedMsg can be up to 3k in size. PassedMsg <drive:path\filename> Like the above, this is the DRIVE:\PATH\FILENAME of Text "Body" for a Welcome Message to leave the New User after a Successful validation was made by the CallBack Verification System. CallBack will also append this file to show a status and give the user this USER I.D. number again for reference. Sample is Called: PASSMSG.CBK, the PassedMsg can be up to 3k in size. (8) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.5 Calling Variables. CallDelay <1 to 60> Delay time in seconds before placing the first call. Some Users have forced DTR set, thus they will not see your DTR drop and hang up. A 30 second timeout will allow the telephone line to time out and reset the line. On the other hand, waiting to long of a time could cause a call collision with a incomming call if you have a busy system. Range 1 to 60 in seconds. Default 5 seconds, recommended a minimum of at least 3 seconds to allow DTR to drop. CallAttempts <1 to 9> The number of times you wish CallBack to try dialing the users phone number if a busy, no-carrier etc. occures. Range 1 to 9, Default 3 AreaCode <number> The AREA CODE of your BBS's phone number. UseAreaCode <Y or N> Areas that REQUIRE using the same Area Code as the one you have for In State Long Distance Calls. If you Uncomment this and answer Y for yes, then CallBack will NOT Strip the Area Code out for Long Diatance Calls within your Area Code and will use in-state Long Distance Dialing as: 1-520-883- 0524. If you leave this commented, then in-state Long Distance will be dialed as: 1-883-0524 This will have No Affect on local calls, or out of your Area Code long distance Calls. If your area does NOT require a Area Code for In State Long Distance Calls, then leave this Comment Out, or Answer N. TollCalls <Y or N> If you want to allow TOLL calls, Answer Y. Default = N for NO long disant calls. (9) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.5 Calling Variables. AreaCodeOK <list> END Area Codes you wish to allow verification for. These can be Free Long Distance call such as a 800 number, or toll numbers you wish to allow in which you need to leave the Area Code number intact. You may also enter Area Codes which are different then yours but are considered local and must have the AreaCode Stripped from the number. This is done by entering a "@" ampersand as the first digit of the Area Code. This tells CallBack to Allow this number and to strip the Area Code from the number. If you need this option, Uncomment the AreaCodeOK option and enter the Area Codes you need, then end it with Uncommenting END statement. Up to 20 entries are permissable, and finish it with the END command. DO NOT add a 1- at the beginning of the number. @602-883 - All Numbers in Area Code 602 with the Prefix of 883 would be allowed and the 602 area code would not be used with the phone number. @520 - All Prefixes in the 520 Area Code would be allowed and the Area Code would not be used with the phone number. 213-976 - All Area Code 213 numbers with the Prefix of 976 would be allowed and the 213 Area Code would be used when calling. 800 - All 800 numbers of any Prefix would be allowed and the Area Code would be used. (10) CallBack 2.0 CallBack CallBack.Cfg Configuration File. 2.5 Calling Variables. LockAreas <list> END If you allow the above TollCalls, these are Long Distance Area Codes you wish to Lock-Out if you have TollCalls 'Y'. Enter the Area Codes after the LockAreas command and finish it with the End Command, or with a Semicolon. Up to 20 Area Codes are supported. EXAMPLE: LockAreas 900 END The above would never permit Callback to place a Call to a Area Code 900 number. (11) CallBack 3.0 CallBack Installation Options. 3.1 Single Node. Make sure you use the DOS Environmental SET command, or you use a command line parameter, or Execute CallBack in the same directory as the CALLBACK.CFG file so CallBack can find it's config file. EXAMPLES: Environment Set: DOS Only - Not Supported for OS/2 Use: SET CBK=C:\CALLBACK Command Line: DOS and OS2 Supported. DOS Use: C:\CALLBACK\CALLBACK.EXE C:\CALLBACK OS/2 Use: C:\CALLBACK\CALLBACK.EXE C:\CALLBACK %P In the Example Above, CallBack will look for CALLBACK.CFG file in the C:\CALLBACK Subdirectory. The %P, (UPPER CASE), in the OS/2 is the MAX Handle for the Comport will be passed to Callback. 3.2 Multi-Node. For MultiLine/Mulitnode systems, you may use a seperate .CFG file for each node. With this option, you cannot use the environmental SET parameter. For CallBack to detect the presence of this, enter a valid drive:path\filename.CFG for each node. EXAMPLE: DOS Use: C:\CALLBACK\CALLBACK.EXE C:\CALLBACK\CBK-%k.CFG OS/2 Use: C:\CALLBACK\CALLBACK.EXE C:\CALLBACK\CBK-%k.CFG %P Note: MAXimus will pass the current node number through the percent k (%k) variable. In the %k examples, CallBack would expect to find .CFG Config files named as this: CBK-1.CFG <--- NODE 1 CBK-2.CFG <--- NODE 2 etc. The %P, (UPPER CASE), in the OS/2 sample is the Comport Handle passed by MAXimus to CallBack. (12) CallBack 4.0 Executing CallBack. 4.1 MAXimus note. Maximus supports on-line user record modification for most exit types. When instructed to do so, it will re-read the lastus##.bbs file for the current node after returning from an external program. If you are running the external program as a menu option, then the fastest way to enable on-line modification is to place the ReRead modifier in front of the usual Xtern_* op-tion. In other words, instead of invoking the program like this for a single line system: Xtern_Dos C:\CBK\CallBack_C:\CBK Demoted "Registration" (or) Xtern_Dos C:\CBK\CallBack_C:\CBK_%P Demoted "Registration" YOU MUST USE A ReRead MODIFIER AS FOLLOWS ReRead Xtern_Dos C:\CBK\CallBack_C:\CBK Demoted "Registration" (or) ReRead Xtern_Dos C:\CBK\CallBack_C:\CBK_%P Demoted "Registration" (13) CallBack 4.0 Executing CallBack. 4.1 MAXimus note. Similarly, you can perform the same operation when using the [xtern_*] MECCA tokens by using an "@" as the first character of the program name. in other words, instead of invoking the program like this for node 1 of a multiline system: MENUS.CTL File Display_File CBK\CallBack Demoted "Registration" CALLBACK.BBS File [xtern_dos]C:\CBK\CallBack.Exe C:\CBK\CBK-%k.CFG (or) [xtern_dos]C:\CBK\CallBack.Exe C:\CBK\CBK-%k.CFG %P YOU MUST USE THE @ (AMPERSAND) INSTEAD [xtern_dos]@C:\CBK\CallBack.Exe C:\CBK\CBK-%k.CFG (or) [xtern_dos]@C:\CBK\CallBack.Exe C:\CBK\CBK-%k.CFG %P NOTE: %P (UPPER CASE) is for OS2 ONLY. NOTE: Your *MUST* have this statement in your MAX.CTL file in the System Section: DOS Close Standard Files If you do not have this statement in your MAX.CTL file, and you have Share Loaded, (DOS Systems), you will get Share Violations. in both DOS and OS/2 Systems. In DOS Systems, If You do not have Share Loaded, then you can damage files that are still open by MAXimus. (14) CallBack 5.0 Operation. 5.1 Consol Keys. When CallBack is in operation, the consol has several toggle keys that the sysop can use. These keys are as follows: ALT-H Help Menu and Fossil Status Key. This key will pop up a window that will show the available consol key, plus the status of the Inbound/Outbound buffers and Carrier Detect. ALT-S Snoop Toggle, (on/off) key. If your default Snoop is off, this toggles it on, if the default is on, this will toggle it off. ALT-C Chat Toggle Key. This will put you into a chat mode with the online user. To exit chat, enter ALT-C to toggle it off. ALT-X Axe the caller. This drops DTR on the caller which will cause MAXimus to recycle as if the caller dropped carrier. 6.0 CBKDAT Utility Program. 6.1 The CBKDAT.EXE program is a un-attended maintenance program for your CALLBAC.DAT file. This program will remove users from the CALLBACK.DAT file that are no longer in your USER.BBS file. CBKDAT.EXE will run un-attended as a nightly event, or whenever you purge users from the USER.BBS file. To Execute CBKDAT.EXE, use the command line switch that will point to your CALLBACK subdirectory as above with CALLBACK.EXE. Single Node Example: C:\CALLBACK\CBKDAT.EXE C:\CALLBACK Multi-Node Example: C:\CALLBACK\CBKDAT.EXE C:\CBK-1.CFG (as Noted Above) C:\CALLBACK\CBKDAT.EXE C:\CBK-2.CFG (etc.) (15) CallBack 7.0 MakeDat Utility. 7.1 GENERAL: MAKEDAT - DOS Specific Utility MAKEDATp - OS/2 Specific Utility MAKEDAT Dual purpose utility to either create or update your CALLBACK.DAT file. If you don't have a CALLBACK.DAT file, it will build it and add all the Verified User Voice and Data phone numbers into the [VERIFIED] section of CALLBACK.DAT. If you have a existing CALLBACK.DAT file, MAKEDAT will scan your exisiting file, scan your MAXimus USER.BBS, and append any Verified Users Voice or Data Phone Number which is not already in your CALLBACK.DAT [VERIFIED] section. 7.2 USAGE: MAKEDAT /P<MAX_path> /C<CallBack_path> /A<privel> /P<MAX-path> This is the full path to your MAXimus Subdirectory where your USER.BBS resides. /C<CallBack_path> This is the full path to your CallBack Subdirectory. /A<privel> This is the minimum MAXimus verified priveledge level which you wish to add to your CALLBACK.DAT file. This Level should equal your CALLBACK.CFG's Privel command Level. If your your CallBack.Cfg file has: Privel 30 Then MAKEDAT's command would be /A30 This level should be a fully qualified level as configured in MAXimus ACCESS.CTL file. (16) 7.3 EXAMPLE: MAKEDAT /Pc:\max /Cc:\max\callback /A30 In the above example, MAKEDAT will look for your USER.BBS File in: C:\MAX Looks for, or Builds New your CALLBACK.DAT in: C:\MAX\CALLBACK And Only Process Users in your USER.BBS with a Minimum Priveledge level of: 30 All Priveledge Levels of above this, including HIDDEN will also be added to your CALLBACK.DAT file. (17)